The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		May 20, 2026 7:26pm

PR Summary

Low Risk
Low risk UI behavior change limited to landing-page shared layouts, though it could subtly affect expected scroll restoration on navigation.

Overview
Adds a new client-only ScrollToTop component that calls window.scrollTo(0, 0) whenever the App Router pathname changes (skipping hash-anchor navigations).

Mounts this component in the shared layouts for blog, integrations, and models so route changes within these shells reliably reset scroll position.

^{Reviewed by Cursor Bugbot for commit 7e926fe. Configure here.}

Greptile Summary

This PR introduces a ScrollToTop client component and mounts it in the blog, integrations, and models shared layouts to work around the documented Next.js App Router behavior (vercel/next.js#64435) where the framework only scrolls the new route segment into view, leaving scroll position unchanged inside shared layouts.

• scroll-to-top.tsx: Minimal useEffect on usePathname that calls window.scrollTo(0, 0); correctly guards against overriding hash-anchor scrolls with if (window.location.hash) return.
• Three layouts (blog, integrations/(shell), models/(shell)): Each mounts <ScrollToTop /> as a null-rendering client island inside the server layout, using the correct @/ alias import path.

Confidence Score: 5/5

Safe to merge — the change is a small, well-scoped client component that renders nothing and only calls window.scrollTo on route changes.

The component is minimal and isolated: it uses standard Next.js hooks, correctly short-circuits on hash anchors, and the three layout files each add a single import and one JSX element with no logic changes. No data, auth, or rendering paths are affected.

No files require special attention.

Important Files Changed

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[User navigates to new pathname] --> B[usePathname change triggers useEffect]
    B --> C{window.location.hash\nnon-empty?}
    C -- Yes --> D[Return early\nBrowser handles anchor scroll natively]
    C -- No --> E[window.scrollTo 0, 0\nReset to top of page]
    E --> F[User sees page from the top]
    D --> G[User lands at hash target]

_{Reviews (8): Last reviewed commit: "refactor(landing-nav): simplify scroll-t..." | Re-trigger Greptile}

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review

@greptile

@cursor review